Dynamic processing system for roadside service control and output generation

ABSTRACT

Aspects of the disclosure relate to a dynamic processing system for roadside service control and output generation. A computing platform may receive map interface information. The computing platform may generate and display a map interface that includes a visual identifier that is centrally located on the map interface and corresponds to a location of the computing platform. The computing platform may receive a location adjustment input adjusting the map interface. The visual identifier may remain centrally located on the map interface while the location adjustment input is received and may correspond to a vehicle location after the location adjustment input is received. After receiving the location adjustment input and based at least in part on a received location confirmation input, the computing platform may send a disabled vehicle indication, which may include the vehicle location and cause dispatch of a service vehicle to the vehicle location.

CROSS-REFERENCE TO RELATED CASES

This application claims priority to U.S. Provisional Application62/754,634, entitled DYNAMIC PROCESSING SYSTEM FOR ROADSIDE SERVICECONTROL AND OUTPUT GENERATION, filed Nov. 2, 2018, the contents of whichare incorporated herein by reference in its entirety for all purposes.

BACKGROUND

Aspects of the disclosure relate to enhanced processing systems forproviding dynamic driving roadside service control and outputgeneration. In particular, one or more aspects of the disclosure relateto dynamic roadside service control platforms that manage requests forservice and determine appropriate service providers.

Many organizations and individuals rely on mobile devices to request arescue or service for a disabled vehicle. In many instances, however,the individual might not be located at their vehicle, and thus GPS datacorresponding to the mobile device might not reflect a location of thevehicle. There remains an ever-present need to develop improvedsolutions to provide roadside service.

SUMMARY

The following presents a simplified summary of various aspects describedherein. This summary is not an extensive overview, and is not intendedto identify required or critical elements or to delineate the scope ofthe claims. The following summary merely presents some concepts in asimplified form as an introductory prelude to the more detaileddescription provided below.

To overcome limitations in the prior art described above, and toovercome other limitations that will be apparent upon reading andunderstanding the present specification, aspects described herein aredirected towards systems and methods for performing dynamic roadsideservice control.

In accordance with one or more embodiments of the disclosure, acomputing platform comprising at least one processor and a memorystoring computer readable instructions may receive map interfaceinformation. Using the map interface information, the computing platformmay display a map interface, which may include a visual identifier thatis centrally located on the map interface and corresponds to a locationof the computing platform. In some instances, the visual identifier maybe located in the exact center of the map interface. In other instances,the visual identifier might not be located in the exact center of themap interface, but may be located within a predetermined distance of theexact center of the map interface. In these instances, the predetermineddistance may be less than a distance between the exact center of the mapinterface and an exterior edge of the map interface. Via a display ofthe computing platform, the computing platform may receive a locationadjustment input corresponding to adjustment of the map interface. Inone or more instances, the visual identifier may remain centrallylocated on the map interface while the location adjustment input isreceived and the visual identifier may correspond to a location of avehicle after the location adjustment input is received. After receivingthe location adjustment input, the computing platform may receive alocation confirmation input. Based at least in part on the locationconfirmation input, the computing platform may send a disabled vehicleindication, which may include the location of the vehicle and may causedispatch of a service vehicle to the location of the vehicle.

In one or more instances, the location of the vehicle may be differentthan the location of the computing platform. In one or more instances,the computing platform may receive a vehicle locator message and one ormore commands directing the computing platform to display a globalpositioning system (GPS) tracking prompt. In these instances, thevehicle locator message may be generated by a dynamic roadside servicecontrol platform in response to a rescue request received from anothercomputing platform.

In one or more instances, the computing platform may determine, usingGPS data corresponding to the visual identifier after the locationadjustment input is received, an address corresponding to the locationof the vehicle. In one or more instances, the computing platform mayreceive an indication of a service provider to be dispatched to thelocation of the vehicle. In these instances, the computing platform maydisplay the indication of the service provider. In one or moreinstances, in response to receiving user input indicating that theservice provider is acceptable, the computing platform may send anindication indicating that the service provider is acceptable.

In one or more instances, the computing platform may receive anindication that a service provider has been dispatched to the locationof the vehicle. The computing platform may display the indication thatthe service provider has been dispatched to the location of the vehicle.

In one or more instances, the computing platform may display theindication that the service provider has been dispatched to the locationof the vehicle by displaying a map interface that indicates progress ofthe service provider from a dispatch location to the location of thevehicle.

These and additional aspects will be appreciated with the benefit of thedisclosures discussed in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIGS. 1A-1B depict an illustrative computing environment for deploying adynamic roadside service control platform that utilizes improvedtechniques for roadside service management and output generation inaccordance with one or more example arrangements discussed herein;

FIGS. 2A-2J depict an illustrative event sequence for deploying adynamic roadside service control platform that utilizes improvedtechniques for roadside service management and output generation inaccordance with one or more example arrangements discussed herein;

FIGS. 3-4 depict illustrative methods for a dynamic roadside servicecontrol platform that utilizes improved techniques for roadside servicemanagement and output generation in accordance with one or more examplearrangements discussed herein;

FIGS. 5-6 depict illustrative user interfaces in accordance withdeploying a dynamic roadside service control platform that utilizesimproved techniques for roadside service management and outputgeneration in accordance with one or more example arrangements discussedherein; and

FIG. 7 depicts an illustrative computing environment for deploying aroadside service module host platform that utilizes improved techniquesfor roadside service management and output generation in accordance withone or more example embodiments.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized, and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

It is noted that various connections between elements are discussed inthe following description. It is noted that these connections aregeneral and, unless specified otherwise, may be direct or indirect,wired or wireless, and that the specification is not intended to belimiting in this respect.

As a brief introduction to the concepts described herein, thisdisclosure is directed towards a system for providing roadsideassistance. In one or more instances, the system may permit a user todesignate, using a mapping application executing on a mobile device, alocation of desired service. Accordingly, the roadside assistance systemmay detect the desired location and dispatch assistance based on thedesignated desired location, rather than merely global positioningsystem (GPS) data of the user's mobile device.

FIGS. 1A-1B depict an illustrative computing environment for deploying adynamic roadside service control platform that utilizes improvedtechniques for roadside service management and output generation inaccordance with one or more example embodiments. Referring to FIG. 1A,computing environment 100 may include one or more computer systems. Forexample, computing environment 100 may include a client device 102, adynamic roadside service control platform 103, a roadside service outputplatform 104, a service dispatch platform 105, an applicationprogramming interface (API) host platform 106, and a service providerdevice 107.

Client device 102 may be a computing device (e.g., smart phone, tabletcomputer, laptop computer, or the like) that may be used to display mapinterfaces and receive user input corresponding to a location of adisabled vehicle. For example, the client device 102 may be used by acustomer of an insurance company or vehicle dealership to identify alocation of their disabled vehicle, and to send the location to theinsurance company or vehicle dealership along with a request for rescue.

As illustrated in greater detail below, dynamic roadside service controlplatform 103 may include one or more computing devices configured toperform one or more of the functions described herein. For example,dynamic roadside service control platform 103 may include one or morecomputers (e.g., laptop computers, desktop computers, servers, serverblades, or the like) configured to receive vehicle location inputs andto dispatch service members accordingly.

In addition, and as illustrated in greater detail below, the dynamicroadside service control platform 103 may be configured to generate,host, transmit, and/or otherwise provide one or more web pages and/orother graphical user interfaces (which may, e.g., cause one or moreother computer systems to display and/or otherwise present the one ormore web pages and/or other graphical user interfaces). In someinstances, the web pages and/or other graphical user interfacesgenerated by dynamic roadside service control platform 103 may beassociated with an external portal provided by an organization, such asa service dispatch portal provided by an insurance institution orvehicle dealership.

Roadside service output platform 104 may include one or more computingdevices configured to perform one or more of the functions describedherein. For example, roadside service output platform 104 may includeone or more computers (e.g., laptop computers, desktop computers,servers, server blades, or the like) configured to determine anappropriate service provider based on a rescue request received and torequest a dispatch accordingly from the service provider.

Service dispatch platform 105 may include one or more computing devicesconfigured to perform one or more of the functions described herein. Forexample, service dispatch platform 105 may include one or more computers(e.g., laptop computers, desktop computers, servers, server blades, orthe like) configured to determine an appropriate employee of the serviceto attend to a rescue request and to send notifications to a device ofthe employee assigning the employee to the rescue request.

The API host platform 106 may be one or more computing devicesconfigured to generate, host, transmit, and/or otherwise provide one ormore web pages and/or other graphical user interfaces (which may, e.g.,cause one or more other computer systems to display and/or otherwisepresent the one or more web pages and/or other graphical userinterfaces). In some instances, the web pages and/or other graphicaluser interfaces generated by the API host platform 106 may correspond tolocal maps that may be adjusted to reflect a user's location.

Service provider device 107 may be a computing device (e.g., laptopcomputer, tablet computer, smart phone, or the like) that may beassociated with an employee of a service provider, and may be used toreceive service assignment indications and map interface informationfrom a service dispatch platform, and to cause display of the assignmentindications and generate map interfaces accordingly. In one or moreinstances, the service provider device 107 may also be used to captureimages or video of a disabled vehicle.

Computing environment 100 also may include one or more networks, whichmay interconnect one or more of client device 102, dynamic roadsideservice control platform 103, roadside service output platform 104,service dispatch platform 105, API host platform 106, and serviceprovider device 107. For example, computing environment 100 may includea network 101 (which may, e.g., interconnect client device 102, dynamicroadside service control platform 103, roadside service output platform104, service dispatch platform 105, API host platform 106, and serviceprovider device 107).

In one or more arrangements, client device 102, dynamic roadside servicecontrol platform 103, roadside service output platform 104, servicedispatch platform 105, API host platform 106, service provider device107, and/or the other systems included in computing environment 100 maybe a type of computing device capable of receiving a user interface,receiving input using the user interface, and communicating the receivedinput to one or more other computing devices, as well as beingconfigured to perform the particular functions described herein. Forexample, client device 102, dynamic roadside service control platform103, roadside service output platform 104, service dispatch platform105, API host platform 106, service provider device 107, and/or theother systems included in computing environment 100 may, in someinstances, be and/or include server computers, desktop computers, laptopcomputers, tablet computers, smart phones, or the like that may includeone or more processors, memories, communication interfaces, storagedevices, and/or other components. As noted above, and as illustrated ingreater detail below, any and/or all of client device 102, dynamicroadside service control platform 103, roadside service output platform104, service dispatch platform 105, API host platform 106, and serviceprovider device 107 may, in some instances, be special-purpose computingdevices configured to perform specific functions.

Referring to FIG. 1B, dynamic roadside service control platform 103 mayinclude one or more processors 111, memory 112, and communicationinterface 113. A data bus may interconnect processor 111, memory 112,and communication interface 113. Communication interface 113 may be anetwork interface configured to support communication between dynamicroadside service control platform 103 and one or more networks (e.g.,network 101, or the like). Memory 112 may include one or more programmodules having instructions that when executed by processor 111 causedynamic roadside service control platform 103 to perform one or morefunctions described herein and/or one or more databases that may storeand/or otherwise maintain information which may be used by such programmodules and/or processor 111. In some instances, the one or more programmodules and/or databases may be stored by and/or maintained in differentmemory units of dynamic roadside service control platform 103 and/or bydifferent computing devices that may form and/or otherwise make updynamic roadside service control platform 103. For example, memory 112may have, store, and/or include a dynamic roadside service controlmodule 112 a, a dynamic roadside service control database 112 b, and amachine learning engine 112 c. Dynamic roadside service control module112 a may have instructions that direct and/or cause dynamic roadsideservice control platform 103 to execute advanced roadside servicecontrol methods for processing rescue requests, as discussed in greaterdetail below. Dynamic roadside service control database 112 b may storeinformation used by dynamic roadside service control module 112 a and/ordynamic roadside service control platform 103 in dynamic roadsideservice control and/or in performing other functions. Machine learningengine 112 c may have instructions that direct and/or cause the dynamicroadside service control platform 103 to perform dynamic roadsideservice control and to set, define, and/or iteratively refineoptimization rules and/or other parameters used by the dynamic roadsideservice control platform 103 and/or other systems in computingenvironment 100.

FIGS. 2A-2J depict an illustrative event sequence for deploying adynamic roadside service control platform 103 that utilizes improvedtechniques to address roadside service requests in accordance with oneor more example embodiments. Referring to FIG. 2A, at step 201, theclient device 102 may establish a connection with the dynamic roadsideservice control platform 103. In one or more instances, the clientdevice 102 may establish a first wireless data connection with thedynamic roadside service control platform 103 to link the client device102 with the dynamic roadside service control platform 103.

At step 202, the client device 102 may establish a voice call sessionwith the dynamic roadside service control platform 103. In one or moreinstances, the voice call session may be established via the firstwireless data connection. In these instances, the client device 102 mayestablish the voice call session to allow a user of the client device102, such as a customer of an insurance institution or vehicledealership, to inform an entity controlling the dynamic roadside servicecontrol platform 103 (e.g., the insurance institution or vehicledealership), that his or her vehicle is disabled and a rescue isrequested. In some instances, rather than establishing the voice callsession with the dynamic roadside service control platform 103, theclient device may send a rescue request indication to the dynamicroadside service control platform 103 while the first wireless dataconnection is established.

At step 203, the dynamic roadside service control platform 103 maygenerate a vehicle locator message and may send the vehicle locatormessage to the client device 102. In one or more instances, the dynamicroadside service control platform 103 may send the vehicle locatormessage via the communication interface 112 while the first wirelessdata connection is established. In sending the vehicle locator message,the dynamic roadside service control platform 103 may send an indicationthat the rescue request has been received and one or more commandsdirecting the client device 102 to display a GPS tracking prompt.Additionally or alternatively, in sending the vehicle locator message,the dynamic roadside service control platform 103 may send a link to amapping interface.

In one or more instances, the dynamic roadside service control platform103 may send the vehicle locator message to a different client devicethan the one that established the voice call session at step 202. Forexample, a parent may use their mobile device to contact the dynamicroadside service control platform 103 on behalf of a child who islocated at a disabled vehicle. In this example, the parent may providethe dynamic roadside service control platform 103 with a phone numberfor the child's mobile device, and the dynamic roadside service controlplatform 103 may send the vehicle locator message to the child's mobiledevice.

At step 204, the client device 102 may receive the vehicle locatormessage and the one or more commands directing the client device 102 todisplay the GPS tracking prompt from the dynamic roadside servicecontrol platform 103. In one or more instances, the client device 102may receive the vehicle locator message and the one or more commandsdirecting the client device to display the GPS tracking prompt while thefirst wireless data connection is established.

At step 205, the client device 102 may display an interface prompting auser to enable GPS tracking. In one or more instances, the client device102 may display an interface that allows a user to select whether or notGPS tracking will be allowed.

Referring to FIG. 2B, at step 206, the client device 102 may receive aGPS acceptance input indicating that access to the client device 102'sGPS data is permitted. In one or more instances, the GPS acceptanceinput may be received as a voice command, a gesture input, a touchinput, or the like.

At step 207, the client device 102 may establish a connection with theAPI host platform 106. In one or more instances, the client device 102may establish a second wireless data connection with the API hostplatform 106 to link the client device 102 to the API host platform 106.

At step 208, the client device 102 may send an indication of the GPSacceptance input to the API host platform 106. In one or more instances,the client device 102 may send the indication of the GPS acceptanceinput to the API host platform 106 while the second wireless dataconnection is established.

At step 209, the API host platform 106 may receive the indication of theGPS acceptance input from the client device 102. In one or moreinstances, the API host platform 106 may receive the GPS acceptanceinput from the client device 102 while the second wireless dataconnection is established.

At step 210, based on the indication of the GPS acceptance input, theAPI host platform 106 may send map interface information. In one or moreinstances, the API host platform 106 may access GPS data correspondingto the client device 102, and may send information to the client device102 that may allow the client device 102 to generate a map interfacecorresponding to a location of the client device.

At step 211, the client device 102 may receive the map interfaceinformation from the API host platform 106. In one or more instances,the client device 102 may receive the map interface information whilethe second wireless data connection is established.

Referring to FIG. 2C, at step 212, the client device 102 may display themap interface using the map interface information received at step 211.In one or more instances, in displaying the map interface, the clientdevice 102 may display a map with a pin indicating a location of theclient device 102. In these instances, the map may be adjustable and thepin may have a fixed position on the display.

At step 213, the client device 102 may receive a map adjustment input.In one or more instances, the user of the client device 102 may haveleft the scene of his or her disabled vehicle or might not have beenpresent at the vehicle (e.g., in the case of a parent and child). Inthese instances, the location of the client device 102 might not be thelocation of the disabled vehicle. Accordingly, the client device 102 mayreceive a user input to drag the map displayed on the client device 102so that the pin is located at the disabled vehicle. In one or moreinstances, to receive the map adjustment input, the client device 102may display a graphical user interface similar to graphical userinterface 505, which is displayed in FIG. 5. In these instances, a pin510 might not be located at the vehicle location (e.g., a user may havewalked away from the vehicle and thus a GPS location of the clientdevice 102 is different than the location of the disabled vehicle). Insome instances, the vehicle might not be displayed on the map interface.In one or more instances, in receiving the map adjustment input, theclient device 102 may adjust the graphical user interface 505 toresemble the graphical user interface 605, which is shown in FIG. 6. Inthese instances, a pin 610 may be located at the vehicle location. Insome instances, the client device 102 might not be located at thevehicle location. In some instances, the pin 510 or 610 may be locatedat the exact center of the graphical user interface. In other instances,the pin 510 or 610 might not be located at the exact center of thegraphical user interface. Rather, the pin 510 or 610 may be located apredetermined distance from the exact center of the graphical userinterface. In these instances, the predetermined distance may be lessthan a distance between the exact center of the graphical user interfaceand an outer boundary of the graphical user interface.

At step 214, the client device 102 may receive a location confirmationinput. In one or more instances, in receiving the location confirmationinput, the client device 102 may receive a user input indicating thatthe map interface has been adjusted to indicate the location of thedisabled vehicle. In one or more instances, in receiving the locationconfirmation input, the client device 102 may receive a gesture input, atouch input, a voice input, or the like.

At step 215, the client device may determine an address corresponding tothe location confirmed at step 214. In one or more instances, the clientdevice may determine the address based on GPS data corresponding to themap interface.

Referring to FIG. 2D, at step 216, the client device 102 may send anindication of the disabled vehicle to the dynamic roadside servicecontrol platform 103. In one or more instances, in sending theindication of the disabled vehicle, the client device 102 may send theaddress of the disabled vehicle along with a request for rescue. In oneor more instances, in sending the indication of the disabled vehicle,the client device 102 may send details corresponding to the disabledvehicle (e.g., vehicle type, issue with the vehicle, or the like). Inone or more instances, the client device 102 may send the disabledvehicle indication to the dynamic roadside service control platform 103while the first wireless data connection is established.

At step 217, the dynamic roadside service control platform 103 mayreceive the disabled vehicle information sent at step 216. In one ormore instances, the dynamic service control platform 103 may receive thedisabled vehicle information via the communication interface 113 whilethe first wireless data connection is established.

At step 218, the dynamic roadside service control platform 103 mayestablish a connection with the roadside service output platform 104. Inone or more instances, the dynamic roadside service control platform 103may establish a third wireless data connection with the roadside serviceoutput platform 104 to link the dynamic roadside service controlplatform 103 with the roadside service output platform.

At step 219, the dynamic roadside service control platform 103 may sendinformation corresponding to the disabled vehicle to the roadsideservice output platform 104. In one or more instances, in sending theinformation corresponding to the disabled vehicle, the dynamic roadsideservice control platform 103 may send information of the vehicle type,the vehicle problem, the location of the disabled vehicle, or the like.In one or more instances, the disabled vehicle information maycorrespond to the disabled vehicle indication received at step 217. Inone or more instances, the dynamic roadside service control platform 103may send the disabled vehicle information to the roadside service outputplatform 104 via the communication interface 113 while the thirdwireless data connection is established.

At step 220, the roadside service output platform 104 may receive thedisabled vehicle information sent at step 219. In one or more instances,the roadside service output platform 104 may receive the disabledvehicle information while the third wireless data connection isestablished.

At step 221, the roadside service output platform 104 may determine aprovider output. In determining the provider output, the roadsideservice output platform 104 may determine a service provider to addressthe rescue request. In one or more instances, the roadside serviceoutput platform 104 may determine the service provider based on thelocation of the disabled vehicle, the issue with the vehicle, or thelike.

Referring to FIG. 2E, at step 222, the roadside service output platform104 may establish a connection with client device 102. In one or moreinstances, the roadside service output platform 104 may establish afourth wireless data connection with the client device 102 to link theroadside service output platform 104 to the client device 102.

At step 223, the roadside service output platform 104 may send aprovider indication to the client device 102 indicating the provideroutput determined at step 221. In one or more instances, the roadsideservice output platform 104 may also send one or more commands directingthe client device 102 to display the provider indication. In one or moreinstances, the roadside service output platform 104 may send theprovider indication to the client device 102 while the fourth wirelessdata connection is established.

At step 224, the client device 102 may receive the provider indicationfrom the roadside service output platform 104. In one or more instances,the client device 102 may receive the provider indication while thefourth wireless data connection is established.

At step 225, the client device 102 may display the provider indication.In displaying the provider indication, the client device 102 may displaya name of the service provider corresponding to the provider output. Inone or more instances, the client device 102 may also display metricsand/or description corresponding to the service provider (e.g., reviews,rating, cost, or the like). In addition, the client device 102 mayprompt the user to accept or reject the service provider via a touchinput, gesture input, voice input, or the like.

At step 226, the client device 102 may receive a provider acceptanceinput indicating that the user accepts the service provider selected bythe roadside service output platform 104. In one or more instances, theclient device 102 might not receive a provider acceptance input and mayreturn to step 221 to have another provider output determined.

Referring to FIG. 2F, at step 227, the client device 102 may send aprovider acceptance indication to the roadside service output platform104. In one or more instances, the client device 102 may send theprovider acceptance indication while the fourth wireless data connectionis established.

At step 228, the roadside service output platform 104 may receive theprovider acceptance indication sent at step 227. In one or moreinstances, the roadside service output platform 104 may receive theprovider acceptance indication while the fourth wireless data connectionis established.

At step 229, the roadside service output platform 104 may establish aconnection with a service dispatch platform 105. In one or moreinstances, the roadside service output platform 104 may establish afifth wireless data connection to link the roadside service outputplatform 104 to the service dispatch platform 105. In one or moreinstances, the roadside service output platform 104 may identify aservice dispatch platform corresponding to the service provider acceptedat step 228 and may establish the connection with that service dispatchplatform.

At step 230, the roadside service output platform 104 may send one ormore commands directing the service dispatch platform 105 to determine aservice driver. In one or more instances, the roadside service outputplatform 104 may send the location of the disabled vehicle to theservice dispatch platform 105 along with the commands. In someinstances, the roadside service output platform 104 may send the one ormore commands directing the service dispatch platform 105 to determinethe service driver while the fifth wireless data connection isestablished.

At step 231, the service dispatch platform 105 may receive a servicedispatch request. For example, the service dispatch platform 105 mayreceive the one or more commands directing the service dispatch platform105 to determine the service driver. In one or more instances, theservice dispatch platform 105 may receive the one or more commandsdirecting the service dispatch platform 105 to determine the servicedriver while the fifth wireless data connection is established.

At step 232, the service dispatch platform 105 may determine a servicedriver output corresponding to a service driver to be assigned to thedisabled vehicle. In one or more instances, the service dispatchplatform 105 may determine the service driver output based on a locationof each service driver in relation to the location of the disabledvehicle. Additionally or alternatively, the service dispatch platform105 may determine the service driver output based on availability ofeach of the service drivers. In one or more instances, the servicedispatch platform 105 may have a predetermined time period within whichto determine the service driver output. In these instances, if a servicedriver output is not determined, the event sequence may return to step221 to determine a new provider output. Additionally or alternatively,the service dispatch platform 105 may be configured to accept or rejectthe service dispatch request automatically or based on a user input. Ifthe service dispatch platform 105 rejects the service dispatch request,the event sequence may return to step 221 to determine a new provideroutput.

Referring to FIG. 2G, at step 233 the service dispatch platform 105 mayestablish a connection with the service provider device 107. In one ormore instances, the service dispatch platform 105 may establish a sixthwireless data connection to link the service dispatch platform 105 tothe service provider device 107. In one or more instances, the serviceprovider device 107 may be associated with a service drivercorresponding to the service driver output determined at step 232.

At step 234, the service dispatch platform 105 may send a serviceindication to the service provider device 107. In sending the serviceindication, the service dispatch platform 105 may send an indication tothe service provider device 107 assigning the service drivercorresponding to the service provider device to the rescue request. Inone or more instances, the service dispatch platform 105 may send one ormore commands directing the service provider device 107 to display aservice interface based on the service indication. In one or moreinstances, the service dispatch platform 105 may send the serviceindication to the service provider device 107 while the sixth wirelessdata connection is established.

At step 235, the service provider device 107 may receive the serviceindication sent at step 234. In one or more instances, the serviceprovider device 107 may receive the service indication while the sixthwireless data connection is established.

At step 236, the service provider device 107 may display a serviceinterface based on the service indication received at step 235. In oneor more instances, in displaying the service interface, the serviceprovider device 107 may display the address/location of the disabledvehicle. In some instances, the service provider device 107 may displaydirections to the location of the disabled vehicle. Additionally, and insome instances, the service provider device 107 may display anindication of the problem with the vehicle (e.g., needs a tow, gasdelivery, flat tire, or the like).

At step 237, the service provider device 107 may establish a connectionwith the dynamic roadside service control platform 103. In one or moreinstances, the service provider device 107 may establish a seventhwireless data connection with the dynamic roadside service controlplatform 103 to link the service provider device 107 to the dynamicroadside service control platform 103.

Referring to FIG. 2H, at step 238, the service provider device 107 mayreceive a route initiation input via a display of the service providerdevice 107. In receiving the route initiation input, the serviceprovider device 107 may receive an indication that the service driver isinitiating a route to the disabled vehicle.

At step 239, the service provider device 107 may send a route initiationindication to the dynamic roadside service control platform 103. In oneor more instances, the service provider device 107 may send the routeinitiation indication to the dynamic roadside service control platformwhile the seventh wireless data connection is established.

At step 240, the dynamic roadside service control platform 103 mayreceive the route initiation indication. In one or more instances, thedynamic roadside service control platform 103 may receive the routeinitiation indication via the communication interface 113 and while theseventh wireless data connection is established.

At step 241, the dynamic roadside service control platform 103 mayforward the route initiation indication to the client device 102. In oneor more instances, the dynamic roadside service control platform 103 mayforward the route initiation indication to the client device 102 via thecommunication interface 113 and while the first wireless data connectionis established.

At step 242, the client device 102 may receive the route initiationindication sent at step 241. In one or more instances, the client device102 may receive the route initiation indication while the first wirelessdata connection is established. In one or more instances, the clientdevice 102 may display the route initiation indication. In displayingthe route initiation indication, the client device 102 may display anotification that the service driver is en route to the disabledvehicle. In some instances, the client device 102 may show a map thattracks progress of the service driver. In some instances, the clientdevice 102 may display an estimated time of arrival of the servicedriver.

At step 243, the service provider device 107 may receive a vehiclearrival input indicating that the service driver has arrived at thedisabled vehicle. In one or more instances, the service provider device107 may receive the vehicle arrival input via a display of the serviceprovider device 107, as a touch input, as a voice input, or othersimilar input methods.

Referring to FIG. 2I, at step 244, the service provider device 107 maysend a vehicle arrival indication based on the vehicle arrival input. Inone or more instances, the service provider device 107 may send thevehicle arrival indication to the dynamic roadside service controlplatform 103 while the seventh wireless data connection is established.

At step 245, the dynamic roadside service control platform 103 mayreceive the vehicle arrival indication sent at step 244. In one or moreinstances, the dynamic roadside service control platform 103 may receivethe vehicle arrival indication via the communication interface 113 andwhile the seventh wireless data connection is established. In someinstances, the dynamic roadside service control platform 103 may displaythe vehicle arrival indication. In displaying the vehicle arrivalindication, the dynamic roadside service control platform 103 may informan employee of an insurance institution or vehicle dealership managingthe rescue request that the service driver has arrived at the disabledvehicle.

At step 246, the service provider device 107 may capture images of thedisabled vehicle. Additionally or alternatively, the service providerdevice 107 may capture video footage of the disabled vehicle.

At step 247, the service provider device 107 may send the images to thedynamic roadside service control platform 103. In one or more instances,the service provider device 107 may send the images to the dynamicroadside service control platform 103 while the seventh wireless dataconnection is established.

At step 248, the dynamic roadside service control platform 103 mayreceive the images and may display the images. This may allow anemployee of the insurance institution or the vehicle dealership toassess damage to the disabled vehicle via the dynamic roadside servicecontrol platform 103. In one or more instances, the dynamic roadsideservice control platform may receive the images via the communicationinterface 113 and while the seventh wireless data connection isestablished.

At step 249, the service provider device 107 may receive a servicecompletion input indicating that service to the disabled vehicle iscompleted (e.g., vehicle has been repaired, successfully towed, or thelike). In receiving the service completion input, the service providerdevice 107 may receive a gesture input, a voice input, a touch input, orthe like.

With reference to FIG. 2J, at step 250, the service provider device 107may send a service completion indication, based on the servicecompletion input, to the dynamic roadside service control platform 103.In one or more instances, the service provider device 107 may send theservice completion indication while the seventh wireless data connectionis established.

At step 251, the dynamic roadside service control platform 103 mayreceive the service completion indication from the service providerdevice 107 and may display the service completion indicationaccordingly. In one or more instances, the dynamic roadside servicecontrol platform 103 may receive the service completion indication viathe communication interface 113 while the seventh wireless dataconnection is established.

Although steps 201-251 describe a single event sequence related to asingle client device, it should be understood that multiple rescuerequests may be processed by the dynamic roadside service controlplatform 103 simultaneously. In one or more instances, the dynamicroadside service control platform 103 may show a large map that tracksmultiple requests. In these instances, if service is delayed for aparticular request, the request may be escalated to a list of highpriority requests. Additionally, the map may show where various servicedrivers are in relation to the disabled vehicles.

FIG. 3 depicts an illustrative method for deploying a dynamic roadsideservice control platform that utilizes improved techniques to addressroadside service requests in accordance with one or more exampleembodiments. To elaborate further, FIG. 3 depicts the event sequenceillustrated by FIGS. 2A-2J from the perspective of the client device.Referring to FIG. 3, at step 305, a computing platform including atleast one processor, a communication interface, and memory may establisha connection with a dynamic roadside service control platform. At step310, the computing platform may establish a voice call session with thedynamic roadside service control platform. At step 315, the computingplatform may determine whether a location of a disabled vehicle isknown. If the location of the disabled vehicle is not known, thecomputing platform may proceed to step 320. If the location of thedisabled vehicle is known, the computing platform may proceed to step335.

At step 320, the computing platform may receive a vehicle locatormessage requesting access to GPS data corresponding to the computingplatform. At step 325, the computing platform may display a prompt foran input to allow access to the GPS data. At step 330, the computingplatform may determine whether access to the GPS data was granted. Ifaccess was not granted, the computing platform may proceed to step 360.If access was granted, the computing platform may proceed to step 335.

At step 335, the computing platform may establish a connection with anAPI host platform. At step 340, the computing platform may send anindication that access to the GPS data is granted to the API hostplatform. At step 345, the computing platform may receive map interfaceinformation from the API host platform based on the GPS data. At step350, the computing platform may display a map interface based on the mapinterface information. At step 355, the computing platform may receive alocation confirmation input indicating that a pin on the map interfacecorresponds to the location of the disabled vehicle. At step 360, thecomputing platform may determine the address of the disabled vehicle. Atstep 365, the computing platform may send an indication of the disabledvehicle including the address to the dynamic roadside service controlplatform. At step 370, the computing platform may establish a connectionwith a roadside service output platform. At step 375, the computingplatform may receive and display a service provider indication. At step380, the computing platform may determine whether an acceptance of theindicated service provider was received. If acceptance was not received,the computing platform may return to step 375 to receive an indicationof a new service provider. If acceptance was received, the computingplatform may proceed to step 385.

At step 385, the computing platform may send an indication of theservice provider acceptance to the roadside service output platform. Atstep 390, the computing platform may receive and display an indicationthat an employee of the service provider is en route to the disabledvehicle.

FIG. 4 depicts an illustrative method for deploying a dynamic roadsideservice control platform that utilizes improved techniques to addressroadside service requests in accordance with one or more exampleembodiments. To elaborate further, FIG. 4 depicts the event sequenceillustrated by FIGS. 2A-2J from the perspective of the dynamic roadsideservice control platform. Referring to FIG. 4, at step 405, a computingplatform including at least one processor, a communication interface,and memory may establish a connection with a client device. At step 410,the computing platform may establish a voice call session with theclient device. At step 415, the computing platform may determine whethera location of a disabled vehicle is already known. If the location ofthe vehicle is already known, the computing platform may proceed to step430. If the location of the vehicle is not already known, the computingplatform may proceed to step 420.

At step 420, the computing platform may generate and send a vehiclelocator message to the client device. At step 425, the computingplatform may receive a disabled vehicle indication indicating thelocation of the vehicle. At step 430, the computing platform mayestablish a connection with a roadside service output platform. At step435, the computing platform may send information corresponding to thedisabled vehicle to the roadside service output platform. At step 440,the computing platform may establish a connection with a serviceprovider device. At step 445, the computing platform may receive anindication that an employee of the service provider is en route to thedisabled vehicle from the service provider device and may display theindication. At step 450, the computing platform may forward the routeinitiation indication to the client device. At step 455, the computingplatform may receive and display an indication that the employee of theservice provider has arrived at the disabled vehicle. At step 460, thecomputing platform may receive and display vehicle images collected bythe service provider device. At step 465, the computing platform mayreceive and display an indication that the employee has completedservice with the disabled vehicle. At step 470, the computing platformmay determine whether outstanding requests for additional disabledvehicles are pending. If so, the computing platform may return to step405. If not, the method may end.

FIG. 7 depicts a roadside service module host platform that utilizesimproved techniques for roadside service management and outputgeneration in accordance with one or more example embodiments. Referringto FIG. 7, roadside service module host platform 701 may include one ormore processors 711 and memory 712. A data bus may interconnectprocessor 711 and memory 712. Memory 712 may include one or more programmodules having instructions that when executed by processor 711 causeroadside service module host platform 701 to perform one or morefunctions described herein and/or one or more databases that may storeand/or otherwise maintain information which may be used by such programmodules and/or processor 711. In some instances, the one or more programmodules and/or databases may be stored by and/or maintained in differentmemory units of roadside service module host platform 701 and/or bydifferent computing devices that may form and/or otherwise make uproadside service module host platform 701. For example, memory 712 mayhave, store, and/or include a plurality of modules for facilitatingroadside service, as described below. It should be understood thatroadside service module host platform 701 may correspond to a singlecomputing device used to host the various modules. In other embodiments,the roadside service module host platform 701 may correspond to multiplecomputing devices used to host the various modules. In these instances,the roadside service module host platform 701 may include one or more ofclient device 102, dynamic roadside service control platform 103,roadside service output platform 104, service dispatch platform 105, APIhost platform 106, service provider device 107, or the like.

Agnostic intake module 712 a may receive requests for rescue fromcustomers, and may allow these requests for rescue to be directlyprocessed by vehicle dealers, mechanics, call centers, or the like.Provider selection module 712 b may implement one or more machinelearning algorithms used to select service providers based on inputssuch as proximity, cost, service type, availability, or the like toimprove dispatch efficiency. Capacity management module 712 c may manageresources involved in multiple rescues and may facilitate tracking ofmultiple rescues occurring for particular service providers, within aparticular geographic region, or the like. In some instances, thecapacity management module 712 c may cause generation and display of anoverall map interface that shows the locations of multiple disabledvehicles and service provider drivers engaged in the various rescues.Predictive analytics module 712 d may profile rescues to predict successrates and/or quality of rescue. If the predictive analytics module 712 ddetermines that a rate or quality of rescue is below a predeterminedthreshold, the predictive analytics module 712 d may escalate thecorresponding rescue request. Status texting module 712 e may permittwo-way texting between a customer device and an automated rescueresponse service. For example, the status texting module 712 e mayprocess a query from the customer device related to arrival of a servicedriver, and may generate/send a response accordingly. Customer viewmodule 712 f may allow vehicle dealers, mechanics, call centers, or thelike to view live rescues (e.g., via an overall map) and may includeindications of the qualities of the rescues. This may allow for yetanother layer of quality control on service driver dispatch. Dealerconnectivity and integration module 712 g may facilitate dispatch ofservice drivers directly from a vehicle dealership, determine when avehicle is en route to the dealership for service, receive advancenotice of repairs to be performed, or the like. Digital walkaroundmodule 712 h may facilitate and process digital photos and videocorresponding to a disabled vehicle (e.g., a 360 degree walk-around viewof the disabled vehicle). In some instances, the digital walkaroundmodule 712 h may also store the corresponding digital photos and videoalong with geotagging information that correlates the photos/video tothe location in which they were captured. In these instances, theroadside service module host platform 701 may determine, based on thegeotagging information and the photos/video, a potential serviceprovider that may assist with the disabled vehicle. For example, theroadside service module host platform 701 may determine the serviceprovider based on one or more of proximity to the disabled vehicle,cost, service type, availability, or the like. In one or more instances,after determining the potential service provider, the roadside servicemodule host platform 701 may generate and send an indication of thepotential service provider to a device that provided the photos/videocontent (e.g., client device 102, or the like). In one or moreinstances, the indication of the potential service provider may prompt auser to accept the potential service provider. For example, the clientdevice 102 may generate a user interface that displays a name of thepotential service provider and prompts a user to select an “accept” or“do not accept” button. In one or more instances, in response toreceiving an indication that the potential service provider isacceptable, the roadside service module host platform 701 may cause adriver of the potential service provider to be dispatched to thelocation of the disabled vehicle. In one or more instances, once thepotential service provider is accepted, the roadside service module hostplatform 701 may generate and send an indication of a type of damage tothe vehicle and an estimated time of arrival of the damaged vehicle atthe service provider. This may allow the service provider to prepare forthe damaged vehicle's arrival and to expedite service to the vehicle.Survey module 712 i may administer, process, and store customersatisfaction surveys related to rescue requests. In some instances,survey module 712 i may use this data to improve overall functionalityof the roadside service module host platform 701.

Spare tire module 712 j may maintain a network of spare tire providers,receive indications of flat tires, dispatch service drivers to one ofthe spare tire providers, administer deposits for the tires, and managereturns of the spare tires. For example, based on video content received(e.g., the video described above with regard to digital walkaroundmodule 712 h) and geolocation information corresponding to a disabledvehicle, the roadside service module host platform 701 may determine atleast one spare tire provider (e.g., dealership, garage, auto partstore, or the like), located within a predetermined distance of thedisabled vehicle. After determining the at least one spare tireprovider, the roadside service module host platform 701 may confirm thatthe at least one spare tire provider does in fact have an availableinventory of spare tires. In one or more instances, the potentialservice provider determined (e.g., as described above with regard to thedigital walkaround module 712 h) may be dispatched to the at least onespare tire provider en route to the disabled vehicle to pick up a sparetire on their way to the disabled vehicle. In one or more instances, thespare tire module 712 j may receive an indication that a spare tireinstalled by the potential service provider has been replaced by aninflated non-spare tire. For example, the service driver may perform aquick tire change to replace a blown tire with a temporary spare tire,and the owner of the vehicle may then drive the vehicle to anotherservice facility to have the temporary spare tire replaced with astandard tire (e.g., they may go to their typical mechanic ordealership, or the like). Once the spare tire has been replaced, thespare tire module 712 j may receive an indication that the spare tirehas been replaced (e.g., from a computing platform corresponding to therepair facility), and the spare tire module 712 j may determine alocation of the now repaired vehicle. After determining a location ofthe repaired vehicle, the spare tire module 712 j may determine a sparetire provider that is closest to the location of the repaired vehicle(e.g., a repository for spare tires). In some instances, this spare tireprovider may be different than the spare tire provider that the driverinitially picked the spare tire up from en route to the disabledvehicle. The spare tire module 712 j may send an indication to theclient device 102, instructing the user to return the spare tire to thedetermined spare tire provider. In one or more instances, the indicationinstructing the user to return the spare tire to the determined sparetire provider may include map interface data that is used to generate amap interface showing a route between the location of the repairedvehicle and the spare tire provider (e.g., provide directions).Accordingly, a network of spare tire providers may be created thatimproves the efficiency of spare tire repairs, pick ups, and deposits.In one or more instances, the spare tire module 712 j may update, at apredetermined interval, a database of spare tire providers and theircorresponding spare tire availability/inventory.

It should be understood that although a number of modules are describedwith regard to the roadside service module host platform 701, it shouldbe understood that the roadside service module host platform 701 mayalso maintain additional modules 712 k, and may add or remove modules atany time.

Roadside service requests may be received by the roadside service modulehost platform 701, routed to one or more appropriate modules, andprocessed accordingly. As a result, the roadside service module hostplatform 701 may provide a modular and flexible computing platform formanaging vehicle rescue requests with robust interactivity features.This may increase provider selection efficiency, upgrade request intakecapability, and allow for more effective case management.

One or more aspects of the disclosure may be embodied in computer-usabledata or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices to performthe operations described herein. Generally, program modules includeroutines, programs, objects, components, data structures, and the likethat perform particular tasks or implement particular abstract datatypes when executed by one or more processors in a computer or otherdata processing device. The computer-executable instructions may bestored as computer-readable instructions on a computer-readable mediumsuch as a hard disk, optical disk, removable storage media, solid-statememory, RAM, and the like. The functionality of the program modules maybe combined or distributed as desired in various embodiments. Inaddition, the functionality may be embodied in whole or in part infirmware or hardware equivalents, such as integrated circuits,application-specific integrated circuits (ASICs), field programmablegate arrays (FPGA), and the like. Particular data structures may be usedto more effectively implement one or more aspects of the disclosure, andsuch data structures are contemplated to be within the scope of computerexecutable instructions and computer-usable data described herein.

Various aspects described herein may be embodied as a method, anapparatus, or as one or more computer-readable media storingcomputer-executable instructions. Accordingly, those aspects may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, an entirely firmware embodiment, or an embodiment combiningsoftware, hardware, and firmware aspects in any combination. Inaddition, various signals representing data or events as describedherein may be transferred between a source and a destination in the formof light or electromagnetic waves traveling through signal-conductingmedia such as metal wires, optical fibers, or wireless transmissionmedia (e.g., air or space). In general, the one or morecomputer-readable media may be and/or include one or more non-transitorycomputer-readable media.

As described herein, the various methods and acts may be operativeacross one or more computing servers and one or more networks. Thefunctionality may be distributed in any manner, or may be located in asingle computing device (e.g., a server, a client computer, and thelike). For example, in alternative embodiments, one or more of thecomputing platforms discussed above may be combined into a singlecomputing platform, and the various functions of each computing platformmay be performed by the single computing platform. In such arrangements,any and/or all of the above-discussed communications between computingplatforms may correspond to data being accessed, moved, modified,updated, and/or otherwise used by the single computing platform.Additionally or alternatively, one or more of the computing platformsdiscussed above may be implemented in one or more virtual machines thatare provided by one or more physical computing devices. In sucharrangements, the various functions of each computing platform may beperformed by the one or more virtual machines, and any and/or all of theabove-discussed communications between computing platforms maycorrespond to data being accessed, moved, modified, updated, and/orotherwise used by the one or more virtual machines.

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one or more of the steps depicted in theillustrative figures may be performed in other than the recited order,and one or more depicted steps may be optional in accordance withaspects of the disclosure.

What is claimed is:
 1. A computing platform comprising: at least oneprocessor; and a memory storing computer readable instructions that,when executed by the at least one processor, cause the computingplatform to: receive map interface information; display, using the mapinterface information, a map interface, wherein the map interfaceincludes a visual identifier that is centrally located on the mapinterface and corresponds to a location of the computing platform;receive, via a display of the computing platform, a location adjustmentinput requesting that the map interface be adjusted to place the visualidentifier at a point on the map interface corresponding to a locationof a vehicle, wherein: the location of the vehicle is different than thelocation of the computing platform, based on receiving the locationadjustment input, the visual identifier remains in a fixed position onthe display corresponding to an exact center of the display, and the mapinterface adjusts, based on the location adjustment input, to place thevisual identifier at a point on the map interface that corresponds tothe location of the vehicle; receive, after receiving the locationadjustment input, a location confirmation input; and send, based atleast in part on the location confirmation input, a disabled vehicleindication, wherein the disabled vehicle indication includes thelocation of the vehicle and wherein sending the disabled vehicleindication causes dispatch of a service vehicle to the location of thevehicle.
 2. The computing platform of claim 1, wherein the location ofthe vehicle is different than the location of the computing platform. 3.The computing platform of claim 1, wherein the memory stores additionalcomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing platform to: receive a vehicle locatormessage and one or more commands directing the computing platform todisplay a global positioning system (GPS) tracking prompt, wherein thevehicle locator message was generated by a dynamic roadside servicecontrol platform in response to a rescue request received from anothercomputing platform.
 4. The computing platform of claim 1, wherein thememory stores additional computer-readable instructions that, whenexecuted by the at least one processor, cause the computing platform to:determine, using GPS data corresponding to the visual identifier afterthe location adjustment input is received, an address corresponding tothe location of the vehicle.
 5. The computing platform of claim 1,wherein the memory stores additional computer-readable instructionsthat, when executed by the at least one processor, cause the computingplatform to: receive an indication of a service provider to bedispatched to the location of the vehicle; display the indication of theservice provider; and in response to receiving user input indicatingthat the service provider is acceptable, send an indication indicatingthat the service provider is acceptable.
 6. The computing platform ofclaim 1, wherein the memory stores additional computer-readableinstructions that, when executed by the at least one processor, causethe computing platform to: receive an indication that a service providerhas been dispatched to the location of the vehicle; and display theindication that the service provider has been dispatched to the locationof the vehicle.
 7. The computing platform of claim 6, wherein displayingthe indication that the service provider has been dispatched to thelocation of the vehicle comprises displaying a map interface thatindicates progress of the service provider from a dispatch location tothe location of the vehicle.
 8. The computing platform of claim 6,wherein the service provider is determined based on the location of thevehicle.
 9. A method comprising: at a computing platform comprising atleast one processor, a communication interface, and memory: receivingmap interface information; displaying, using the map interfaceinformation, a map interface, wherein the map interface includes avisual identifier that is centrally located on the map interface andcorresponds to a location of the computing platform; receiving, via adisplay of the computing platform, a location adjustment inputrequesting that the map interface be adjusted to place the visualidentifier at a point on the map interface corresponding to a locationof a vehicle, wherein: the location of the vehicle is different than thelocation of the computer platform, based on receiving the locationadjustment input, the visual identifier remains in a fixed position onthe display corresponding to an exact center of the display, and the mapinterface adjusts, based on the location adjustment input, to place thevisual identifier at a point on the map interface that corresponds tothe location of the vehicle; receiving, after receiving the locationadjustment input, a location confirmation input; and sending, based atleast in part on the location confirmation input, a disabled vehicleindication, wherein the disabled vehicle indication includes thelocation of the vehicle and wherein sending the disabled vehicleindication causes dispatch of a service vehicle to the location of thevehicle.
 10. The method of claim 9, wherein the location of the vehicleis different than the location of the computing platform.
 11. The methodof claim 9, further comprising: receiving a vehicle locator message andone or more commands directing the computing platform to display aglobal positioning system (GPS) tracking prompt, wherein the vehiclelocator message was generated by a dynamic roadside service controlplatform in response to a rescue request received from another computingplatform.
 12. The method of claim 9, further comprising: determining,using GPS data corresponding to the visual identifier after the locationadjustment input is received, an address corresponding to the locationof the vehicle.
 13. The method of claim 9, further comprising: receivingan indication of a service provider to be dispatched to the location ofthe vehicle; displaying the indication of the service provider; and inresponse to receiving user input indicating that the service provider isacceptable, sending an indication indicating that the service provideris acceptable.
 14. The method of claim 9, further comprising: receivingan indication that a service provider has been dispatched to thelocation of the vehicle; and displaying the indication that the serviceprovider has been dispatched to the location of the vehicle.
 15. Themethod of claim 14, wherein displaying the indication that the serviceprovider has been dispatched to the location of the vehicle comprisesdisplaying a map interface that indicates progress of the serviceprovider from a dispatch location to the location of the vehicle. 16.One or more non-transitory computer-readable media storing instructionsthat, when executed by a computing platform comprising at least oneprocessor, a communication interface, and memory, cause the computingplatform to: receive map interface information; display, using the mapinterface information, a map interface, wherein the map interfaceincludes a visual identifier that is centrally located on the mapinterface and corresponds to a location of the computing platform;receive, via a display of the computing platform, a location adjustmentinput requesting that the map interface be adjusted to place the visualidentifier at a point on the map interface corresponding to a locationof a vehicle wherein: the location of the vehicle is different than thelocation of the computing platform, based on receiving the locationadjustment input, the visual identifier remains in a fixed position onthe display corresponding to an exact center of the display, and the mapinterface adjusts, based on the location adjustment input, to place thevisual identifier at a point on the map interface that corresponds tothe location of the vehicle; receive, after receiving the locationadjustment input, a location confirmation input; and send, based atleast in part on the location confirmation input, a disabled vehicleindication, wherein the disabled vehicle indication includes thelocation of the vehicle and wherein sending the disabled vehicleindication causes dispatch of a service vehicle to the location of thevehicle.
 17. The one or more non-transitory computer-readable media ofclaim 16, wherein the location of the vehicle is different than thelocation of the computing platform.
 18. The one or more non-transitorycomputer-readable media of claim 16, wherein the memory storesadditional computer-readable instructions that, when executed by the atleast one processor, further cause the computing platform to: receive avehicle locator message and one or more commands directing the computingplatform to display a global positioning system (GPS) tracking prompt,wherein the vehicle locator message was generated by a dynamic roadsideservice control platform in response to a rescue request received fromanother computing platform.
 19. The one or more non-transitorycomputer-readable media of claim 16, wherein the memory storesadditional computer-readable instructions that, when executed by the atleast one processor, further cause the computing platform to: determine,using GPS data corresponding to the visual identifier after the locationadjustment input is received, an address corresponding to the locationof the vehicle.
 20. The one or more non-transitory computer-readablemedia of claim 16, wherein the memory stores additionalcomputer-readable instructions that, when executed by the at least oneprocessor, further cause the computing platform to: receive anindication of a service provider to be dispatched to the location of thevehicle; display the indication of the service provider; and in responseto receiving user input indicating that the service provider isacceptable, send an indication indicating that the service provider isacceptable.
 21. The one or more non-transitory computer-readable mediaof claim 16, wherein the memory stores additional computer-readableinstructions that, when executed by the at least one processor, furthercause the computing platform to: receive an indication that a serviceprovider has been dispatched to the location of the vehicle; and displaythe indication that the service provider has been dispatched to thelocation of the vehicle.